Repository navigation
Add a cloud-cost page and link it from the README - #24
Merged
Merged
Conversation
docs/cloud-savings.md states the three costs a PDF library puts on a service - the licence, the native code, and the CPU and memory - and turns the measured 100 MB allocation and wall time into a bill. The tariff and the commercial seat price are labelled as illustrative; the formulas are the contract, and the page lists what it does not claim (no competitor benchmark, one machine, an assumed GC throughput). The README links it from the intro and the documentation section, and docs/README.md links it from the manual index.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A page that turns the measured allocation and CPU time into money, linked from the README, with every price labelled as illustrative.
docs/cloud-savings.md— the three costs (licence, native code, CPU/memory), the measured 100 MB table fromdocs/measurements.md§10, the AOT figures, and a cost model with the tariff left as a value to replace.README.md— linked from the intro (“What it saves you”) and from the Documentation section.docs/README.md— linked from the manual index.The model, in one line
A 100 MB merge allocates 104.2 MB instead of 204.2 MB and finishes 67.5 ms sooner (ADR-004). At 1,000,000 merges a month that is 100 TB of allocation avoided, worth about $1–4 a month on an illustrative $0.04/vCPU-hour + $0.005/GB-hour tariff; the licence line (a $1,500 seat × 20 developers = $30,000/year) is the saving with the order of magnitude more weight. The page says so rather than hiding it.
What it does not claim
No comparison to a named library, no quote, one machine, and an assumed 1 GB/s GC throughput. The page lists all four so the numbers can be replaced with the reader's own.
Evidence
Docs only:
dotnet build -c Release→ 0 warnings, 0 errors;dotnet test→ 1242 passed on each leg (no code changed).